Client side system and method for search backed calendar user interface

ABSTRACT

A method is provided to produce a custom calendar user interface (UI) display on an electronic device display screen comprising: providing a search query to a user device; sending the search query over the network to a server system; receiving over the network by one or more user devices from a server system, information that identifies one or more code objects that match the search query; using the identified one or more identified code objects by the one or more user devices to generate one or more visual content items within a calendar user interface (UI) grid display on their device display screens.

BACKGROUND

Electronic calendars typically display calendar entries based uponindividual predetermined lists of events, such as a calendar for asingle person, single room, or single project. While some priorcalendars allow overlaying of multiple lists on the same view, theygenerally have limited capability to enable dynamic combinations andselection of entries across multiple lists. While calendars have beenemployed routinely to plan and organize activities, they generally havenot been used for dynamic communication and dynamic information sharing.There is a need for an electronic calendar system that facilitatesdynamic communication and dynamic information sharing to therebyfacilitate collaboration and the organization, management of people andprojects.

SUMMARY

In one aspect, a method is provided to produce a custom calendar userinterface (UI) display on an electronic device display screen. A searchquery is provided to a user device. The search query is sent over anetwork to a server system. One or more user devices receive from aserver system over the network information that identifies one or morecode objects that match the search query. The one or more user devicesuse the identified code objects to generate one or more visual contentitems within a calendar user interface (UI) grid display on their devicedisplay screens.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is an illustrative drawing of a calendar user interface (UI)instance showing Saturday and Sunday date panes collapsed in inaccordance with some embodiments.

FIG. 1B is an illustrative drawing of another calendar user interface(UI) instance showing Saturday and Sunday date panes expanded inaccordance with some embodiments.

FIG. 1C is an illustrative drawing of the calendar user interface (UI)instance of FIG. 1B showing a week expanded in accordance with someembodiments.

FIG. 1D is an illustrative drawing representing a process to expand andcompact date panes in a calendar UI instance, in accordance with someembodiments.

FIG. 2 is an illustrative generalized flow diagram representing ingeneral terms activities performed by client user devices and by aserver system and the flow of information between them in accordancewith some embodiments.

FIG. 3 is an illustrative drawing of an example of a first userinterface screen display to receive user input to define a new visualcontent item for display within a calendar UI in accordance with someembodiments.

FIG. 4 is an illustrative drawing of an example expanded view of avisual content item in accordance with some embodiments.

FIG. 5 is an illustrative drawing showing a portion of an example codeobject stored in a computer readable storage device in accordance withsome embodiments.

FIG. 6 is an illustrative drawing of an example second user interfacescreen display to receive user input to specify a search query to definea new calendar UI instance in accordance with some embodiments.

FIG. 7 is an illustrative flow diagram representing a process to producea searchable task attribute information structure in accordance withsome embodiments.

FIG. 8 is an illustrative drawing of a table that identifies multipledifferent kinds of example task attributes and provides briefdescriptions of some of them in accordance with some embodiments.

FIG. 9 is an illustrative flow diagram representing a server systemprocess to match search query to code objects and to chronologicallyorder code objects in accordance with some embodiments.

FIG. 10 is an illustrative drawing representing an examplechronologically ordered set of the code objects stored in a computerreadable storage device produced according to the process of FIG. 9 inaccordance with some embodiments.

FIG. 11 is an illustrative flow diagram representing a chronologicalsearch and mapping process in accordance with some embodiments.

FIG. 12 is an illustrative drawing representing an example calendar UIinformation structure in accordance with some embodiments.

FIG. 13 is an illustrative drawing that represents an example date paneinformation structure in accordance with some embodiments.

FIG. 14 is an illustrative drawing of a list UI instance thatcorresponds to the calendar UI instance of FIG. 1 in accordance withsome embodiments.

FIG. 15 is an illustrative flow diagram representing a process togenerate a list view UI instance in accordance with some embodiments.

FIG. 16 is an illustrative drawing representing rendering of alternativerepresentations of a calendar UI information structure of FIG. 12 inaccordance with some embodiments.

FIG. 17 is an illustrative drawing representing a process to determinenumber of rows of a calendar UI instance to display in accordance withsome embodiments.

FIG. 18 is an illustrative drawing representing a process to determinewhether to display scrolling to a selected date pane or to display ajump to a selected date pane in accordance with some embodiments.

FIG. 19 is an illustrative drawing representing in general terms networkcommunications between multiple user devices and a server device inaccordance with some embodiments.

FIG. 20 is a block diagram of machine in the example form of a computersystem within which a set instructions, for causing the machine toperform any one or more of the methodologies discussed herein, may beexecuted.

DESCRIPTION OF EMBODIMENTS

The following description is presented to enable any person skilled inthe art to create and use a computer system configuration and relatedmethod and article of manufacture to produce and use a calendar userinterface in accordance with some embodiments. Various modifications tothe embodiments will be readily apparent to those skilled in the art,and the generic principles defined herein may be applied to otherembodiments and applications without departing from the spirit and scopeof the invention. Moreover, in the following description, numerousdetails are set forth for the purpose of explanation. However, one ofordinary skill in the art will realize that the invention can bepracticed without the use of these specific details. In other instances,well-known data structures and processes are shown in block diagram formin order not to obscure the description of the invention withunnecessary detail. Identical reference numerals may be used torepresent different views of the same item in different drawings. Flowdiagrams in drawings referenced below are used to represent processes.One or more computer systems are configured to perform these processes.The flow diagrams include modules that represent the configuration of acomputer system according to computer program code to perform the actsdescribed with reference to these modules. Thus, the present inventionis not intended to be limited to the embodiments shown, but is to beaccorded the widest scope consistent with the principles and featuresdisclosed herein.

Definitions

As used herein a “visual content item” refers to an object that isvisible within a date pane of a calendar date pane display grid producedon a display screen and that may have associated visible informationcontent such as text and graphics, for example. A visual content itemmay include user interface controls such as buttons and menus for use indisplay, editing and searching, for example. A visual content objecttypically is associated with one or more searchable attributes, such astext that it may contain or entries in information fields that it maycontain, for example.

As used herein a “code object” refers to electronic device readable codethat corresponds to a visual content item and that is used by anelectronic device to generate the corresponding visual content item. Acode object typically is associated with one or more searchableattributes, that in turn, correspond to attributes of its correspondingvisual content item, for example.

Calendar User Interface

FIG. 1A is an illustrative drawing of a calendar user interface (UI)instance 102 in accordance with some embodiments. A date pane fieldincludes a two dimensional display grid of date panes that correspond todays and weeks of the month. As used herein a “date pane” refers to aphysical region of a calendar UI display associated with a single date.The region typically is rectangular in shape. A date pane typicallyincludes an indication of the day of the month or week that itrepresents. For example, a date pane containing the number 22 mayindicate that it corresponds to the 22^(nd) day of the month. Visualcontent items displayed with date panes provide information such as taskidentification, identification of persons responsible for tasks andstatus of tasks. Different users provide calendar entry information thatis stored for use to produce different visual content items.

A scrollable display grid template within the calendar UI includescolumns and rows of date panes. Each date pane corresponds to adifferent day of the month, which is indicated in the top left corner ofeach pane. Each column of date panes corresponds to a day of the week,which is listed above the top row of the display grid template, i.e.Mon, Tues, etc. Each row of date panes corresponds to seven days of aweek. Each row begins with Sunday and ends with a Saturday. In theexample view of the calendar UI instance in FIG. 1A, all of the datepanes corresponding to Sundays and Saturdays are collapsed so as to showonly the day of the month of each Sunday and each Saturday. In otherwords, illustrative FIG. 1A calendar UI includes full expanded views ofpanes, which hide visual content items displayed within them for each ofMonday-Friday, and has collapsed views of panes, which hide visualcontent items displayed within them for Sunday and Saturday. The datepanes for Sunday and Saturday are collapsed to make more screen spaceavailable for display of visual content items within the days of thetypical work week. The collapsed date panes may include indicia toindicate that a visual content item is associated with the date pane.For example, in some embodiments a collapsed date pane includes a dot toindicate that a visual content item is associated with the collapseddate pane. In FIG. 1A, the collapsed pane corresponding to Sunday the15^(th) of the month includes a dot 108 that acts as an indicator thatthe pane when in expanded form includes one or more visual contentitems. In the collapsed form shown in FIG. 1A, those visual contentitems are hidden, but the dot 108 indicates their existence. It will beappreciated that when a date pane is collapsed, there is insufficientspace to show its associated visual content item.

In the example view of the calendar UI instance in FIG. 1B is anillustrative drawing of a different calendar UI instance with date panescorresponding to Sundays and Saturdays displayed in expanded form so asto show content information items associated with the Saturday andSunday date panes. The date pane for Saturday the 30^(th) displays acontent item labeled “yev's post”. Comparing FIG. 1A and FIG. 1B, whichdisplay different calendar instances, it can be seen that with theSaturday and Sunday date panes open, the size of the Monday throughFriday date panes is reduced leaving reduced space for the display ofassociated visual content items. Referring to the calendar UI instanceof FIG. 1B, the date pane for Thursday the 4^(th) of the month, containsa list of content items ends with an indicator “2 more . . . ”indicating that there are additional visual display items associatedwith that date pane. In accordance with some embodiments, the column ofdate panes for Sunday and Saturday can be selectively collapsed andexpanded through user input such as pointing and clicking, for example.

The number of weeks displayed in a calendar UI can be adjusted dependingupon how many weeks will fit in the height of a browser window (notshown) or other screen display area used by a device displaying theCalendar UI. The illustrative calendar UI displays four weeks. Differentbrowser windows and different devices may have different display regiondimensions such as different heights and widths. Thus in some end-userdevices, the number of weeks displayed within a calendar UI depends uponavailable device display area.

The current day of the month is indicated by a current date marker,which in some embodiments includes star symbol. In the illustrativecalendar UI instance of FIG. 1A, the current date is the 26^(th) of themonth and the date pane representing the 26^(th) contains a star. In theillustrative calendar UI instance of FIGS. 1B-1C, the current date isthe 4^(th) of the month and the date pane representing the 4^(th)contains a star. A date pane representing the first day of a monthincludes a new month marker, which in some embodiments includes a heavyhorizontal line adjacent to an indication of the month. In theillustrative example calendar UI instance of FIG. 1A, the date panerepresenting the numerical 1^(st) day of the month, which happens tofall on a Tuesday, includes a heavy horizontal line across its topportion and the indication “Jul 1” adjacent to the horizontal line.Similarly, in the illustrative example calendar UI instance of FIGS.1B-1C, the date pane representing the numerical day of the 1^(st) day ofthe falls on a Monday and includes a heavy horizontal line across itstop portion and the indication “Dec 1” adjacent to the horizontal line.Note that in accordance with some embodiments, the date panerepresenting the first day of the month indicates the month, e.g., “Jul”or “Dec”, within the pane itself, but other panes do not include a monthindicator. In the illustrative embodiment, a calendar view date rangeindication, which indicates the range of dates currently visible onscreen within the calendar UI, is displayed across the top of thecalendar UI. In the illustrative calendar UI of FIG. 1A, the calendarview range indicates, “Jun 15-Jul 12, 2014”, and in the illustrativecalendar UI of FIGS. 1B-1C, the calendar view range indicates, “Nov 23-Dec 27, 2014” The calendar view range indication changes automaticallywith changes in the range of dates represented in the calendar UI.

Shading of date panes demarcates changes from one month to the next.More specifically, background shading of date panes gradually changesbetween the first and last day of the month. In accordance with someembodiments, the first day of the months is the least shaded, i.e. hasthe lightest background shading, and the last day of the month has thegreatest shading, i.e. has the darkest background shading. Morespecifically, in accordance with some embodiments, each successive dayof the month becomes progressively darker starting with white on thefirst day of a month and changing to the darkest shading on the last dayon the month. In other words, panes corresponding to days between thefirst and last days of the month become progressively darker the fartherthey are from the first day of the month and the closer they are to thelast day of the month. This shading pattern recurs for each month. Insome embodiments, the shading level varies linearly from one day of themonth to the next. For example, assuming that a lightest shading levelis represented by the number 1 and that a darkest shading level isrepresented by the number 31, the first day of the month has shadinglevel 1, the second day of the month has a slightly darker shading level2, the third day of the month has shading level 3, etc. Thus, a user isalerted to a transition from one month to the next, not only by the newmonth marker and the month indicator on the first day of the month, butalso by a sharp transition in shading between the darkest backgroundlast day of a previous month and the lightest background first day of anext month. Alternatively, the shading pattern can be reversed with thefirst day of the month being the most heavily shaded and the last day ofthe month being the least heavily shaded.

A lightweight feel to the calendar UI instances is achieved at least inpart through the use of lightly shaded horizontal lines to provide avisible demarcation between rows and through an absence of verticallines between columns of date panes. As with a conventional calendar,the panes in each vertical column correspond to the same day of the weekfor the month, and the panes in each horizontal row correspond to daysof one week of the month. A demarcation between vertical columnboundaries is provided by a numerical indication of the day of the monthin the upper left side of each pane. Individual panes also may includecontent information. The use of lightly shaded horizontal lines and theabsence of vertical lines limit distraction from content informationdisplayed within panes of the calendar UI and can have the effect ofmaking the content stand out more prominently.

The calendar UI instances include a search query input field disposedabove the date pane display grid in the illustrative calendar UIinstance in which a user can enter a search query used to identifyvisual content items displayed within date panes of the calendar UI. Thesearch query specifies search terms selected by the user for use tosearch for matching visual content items to be displayed within the datepanes of the calendar UI instance. A calendar instance is defined usingthe search query field content. More specifically, a search querydetermines visual content information included within date panes of thecalendar UI instance and thereby defines the calendar UI instance. Asexplained below, a calendar UI instance is defined through a search forvisual content items that match the search query within the calendar UIinstance search query field that are then displayed within date panes ofthe calendar UI instance to define the calendar UI instance. The visualcontent items may have been created by the user who enters the searchquery or by other users. Thus, a search query may result in displaywithin a calendar UI instance of visual content items created bydifferent users. The calendar UI instance of FIG. 1A includes theillustrative example search query, “Tasks in Weekly Marketing MeetingAgenda, Marketing & Sales Material, or Goals Q2 2014” shown displayedwithin the search field. The example visual content items displayedwithin the illustrative calendar UI instance of FIG. 1A were selected inresponse to the illustrative query in that calendar UI instance. Thecalendar UI instance of FIGS. 1B-1C includes the illustrative examplesearch query, “Items in Weekly Marketing Meeting Agenda, Marketing &Sales Material, or Company Goals/KRs” shown displayed within the searchfield. The example visual content items displayed within theillustrative calendar UI instance of FIGS. 1B-1C were selected inresponse to the illustrative query in that calendar UI instance.

The user who defines the search query also may specify which other usersshould have access to a calendar UI generated using the search query.Users who are given access to the resulting calendar UI may have itdelivered automatically to their devices or alternatively, may berequired to request it or download it, for example. Thus, a calendar UIdefined by an (or more) individual is shared with multiple users forplanning, communication and collaboration.

A date selection field indicates a date range currently displayed withinthe calendar UI date pane display grid. In the example calendar UIinstance of FIG. 1A, for example, the date range is “Jun 15-Jul. 12,2014”. A user may enter a date range in the date selection field 106 toselect a date range to be displayed within the display grid. Inaccordance with some embodiments, in the absence of user input to thedate selection field, the calendar UI defaults to use the current dateas a reference date to determine the date range to display within thecalendar display grid. User input of a new date range in the dateselection field results in a calendar UI jump to the new date range andto display of calendar UI items associated with dates in the new daterange. The illustrative calendar UI instance displays multiple visualcontent items. As explained more fully below, visual content items aregenerated using corresponding code objects stored in a non-transitorycomputer readable storage device. User entries from different users candefine different code objects, which in turn, can be used to generatedifferent visual content items. The visual content items visible withinthe date panes of a given calendar UI instance are determined based upona user-provided search query that defines the given calendar UIinstance.

Date pane size can be varied in accordance with some embodiments. Visualcontent items are displayed within date panes. However, there may bemore visual content items associated with a given date pane than can bedisplayed within a normal size date pane. In accordance with someembodiments, date pane size can be selectively expanded to display agreater number of visual content items than a number that can bedisplayed when the date pane is normally sized. In accordance with someembodiments, an entire row of date panes is expanded or compacted inunison. Expanding an entire row, which represents a week, advantageouslyprovides a user with visual content item detail for multiple days andnot just a single one facilitating visualization of tasks on a crowdedcalendar. Moreover, during normal operation, weekend date panes arecompacted so that none of their associated visual content items arevisible during normal operation. However, in response to a user request,weekend date panes can be expanded to display their associated visualcontent items. When weekend date panes are expanded, correspondingweekday date panes are correspondingly compacted to make room for themwithin the calendar UI.

A visual content item may include multiple different pieces ofinformation. A visual content item may represent an activity. An itemthat represents an activity may display a label naming the activity,status (e.g., completed, overdue), relatedness to other items (e.g., viacolor), and other information. FIG. 4 , which is explained more fullybelow is an illustrative drawing showing the visual UI item from “Jul 1”in the calendar UI instance of FIG. 1A. In accordance with someembodiments, the visual content items within date panes can beselectively collapsed and expanded through user input such as pointingand clicking, for example.

The date panes of the calendar UI weeks are expandable so as to increasethe amount of information displayed by visual content display itemswithin an expanded week. FIG. 1C is an illustrative drawing showing theweek Nov 30 to Dec 6 in FIGS. 1B-1C in expanded form. In FIG. 1C, theweekend date panes are shown in compacted, unexpanded form. Note thatthe date pane for the 30^(th) includes a dot 108, which indicatescontent of that date pane that is not visible in the compacted form.Recall that the content of the 30^(th), “yev's post” is displayed in theexpanded from shown in FIG. 1B. A date pane that is associated withmultiple visual display items may have insufficient space to display allof its associated items when not expanded. Note that in FIG. 1B, thedate pane representing the 6^(th) in unexpanded form has the notation,“2 more . . . ”, indicating that the date pane includes two more visualcontinent items that are not currently visible. In FIG. 1C, the datepane representing the 6^(th) in expanded form shows those “two more”visual content items. By expanding the week in which the date pane isdisposed, items become visible that were hidden (not visible) when theweek was not expanded. In accordance with some embodiments, the heightof a row (i.e. a week) in expanded form depends upon the number ofvisual content items to be displayed. Thus, for example, if the datepane representing the 6^(th) included more visual content items and notjust “2 more”, then it would be even wider in its expanded from.

Visual content items appearing within different date panes may berelated to each other. For example, task items in different panes may berelated to the same project. In accordance with some embodiments, thecalendar UI includes a content item association indicator. In someembodiments color coding acts as a content item association indicator.More specifically, color coding is used to create a visible associationamong displayed content items. For example, all items associated with afirst project may be associated with a first color (e.g., orange); allvisual content items associated with a second project may be associatedwith a second color (e.g., green); and all visual content items that arenot associated with a project have no special background, and thereforeare displayed with a third (default) color (e.g., white) as background.

For example, a project may involve development of a marketing plan for anew product. Some visual content items associated with the marketingproject may represent tasks to be performed in connection with theproject, for example. Other visual content items associated with themarketing project may represent persons who are involved with performingthe tasks, for example. More specifically, for example, certain visualcontent items shown within the date panes of the illustrative calendarUI instances of FIG. 1A and of FIGS. 1B-1C represent tasks. Other visualcontent items may represent other aspects of the marketing plan.

Referring to the calendar UI instance of FIG. 1A, for example, firstvisual content items indicated within the date panes for June 18, 23 and26 and July 4 represent four different tasks that are associated with afirst project. The first project corresponds to the first color (e.g.,orange), and accordingly, the task items associated with the date panesfor June 18, 23 and 26 and July 4 are displayed with the first color(orange) as background. The task associated with June 18, for example,is described as “[10] beta for calendar or entire team”, which may meanthat on June 18, the person assigned this task will perform a 10 minutetest, for observation by the entire marketing team, of the new calendarsoftware. Similarly, second visual content items indicated in theexample calendar UI within the date panes for June 26 and 30 representtasks associated with a second project that is associated with thesecond color (e.g., green). Accordingly, the task items associated withthe date panes for June 26 and 30 are displayed with the second color(green) as background. However, third visual content items indicated inthe example calendar UI within the date panes for June 26 and July 1represent two different tasks that are not associated with a particularproject. Accordingly, these task items within the date panes for June 26and July 1 are displayed with no special background color and insteadare displayed on a (default) a color (white) as background.

Continuing to refer to the calendar UI instance of FIG. 1A, for example,other visual content items are shown within the date panes of theillustrative calendar UI instance represent persons, for example.Specifically, photos of persons responsible for tasks associated withthe first project are overlaid within first visual content itemsrepresenting the first color coded tasks shown on the date panes forJune 18, 23 and 26 and July 4. Similarly, photos of persons responsiblefor tasks associates with the second project are overlaid within secondvisual content items representing the second color coded tasks shown onthe date panes for June 26 and 30. Likewise, photos of personsresponsible for tasks associated with the third project are overlaidwithin third visual content items representing third non-color codedtasks shown on the date panes for June 26 and July 1.

Another example visual content item shown within the date panes of theillustrative calendar UI instance of FIG. 1A, for example, representsstatus of a task. Specifically, for example, the check mark overlaidwithin the third visual content item representing a third colornon-coded task associated with the date pane June 26 indicates that thetask described as, “Send out June Newsletter”, has been completed.

Yet another visual content item shown within the date panes of theillustrative calendar UI instance of FIG. 1A, for example, represents atag, for example. The box icon shown overlaid within the first task itemassociated with the June 26 date pane and the box icon overlaid withinthe second task item associated with the June 30 date pane representtags that may be used to associate these task items with one or morekeywords, for example. Thus, for example, both tags may be associated ina non-transitory storage device (not shown) with the keyword “budget”,such that a search query that includes the term “budget” can be used toidentify the first and second projects.

Process to Expand and Compact Date Panes

FIG. 1D is an illustrative drawing representing a process 150 to expandand contract date panes in a calendar UI instance, in accordance withsome embodiments. Module 152 configures a computer system to receivevisual display item information for display in one or more date panes.The information may include one or more code objects used by thecomputer system to generate visual display items within a date pane.Module 154 configures the computer to fit the visual display objectswithin normal size date panes. Normal size date panes are large enoughto display to display some but not necessarily all associated visualcontent items. Normal size date panes are displayed during normaloperation when no expansion or compaction of date pane size is invoked.The normal size date pane for Jul 4^(th) in FIG. 1A, for example, islarge enough to display at least three visual content items, and it hasadditional space to display even more of them. If there are too manyvisual content items associated with a given normally sized date pane,then some of the visual content items will not be displayed, andinstead, an indicator may be provided such as “2 more” to indicate thatthe date pane is associated with visual content items that are notcurrently displayed.

Decision module 156 configures the computer to determine whether a userrequest to expand a pane has been received. A request to expand mayinclude user pointing and clicking on a region of a date pane inaccordance with some embodiments, for example. Decision module 156 waitsfor a user input received requesting date pane expansion, as indicatedby module 160. Decision module 162 configures the computer to determinewhether a received user request to expand is a request to expand aweekday date pane. A user may make a request to expand a weekday pane byselecting a prescribed region of a date pane in accordance with someembodiments.

In response to a determination by decision module 162 that the receivedrequest is a request to expand a weekday date pane, module 164 expandsthe selected weekday date pane to be tall enough to fully displayadditional visual display items associated with the selected date panethat were not displayed previously. Module 164 configures the computerto also expand by the same amount all other panes in the same row as thedate pane selected for expansion. Alternatively, the user selection maybe a selection of a date pane row for expansion, which results inexpansion of all date panes in the row to be tall enough to displayadditional visual display items associated with date panes in theselected row that were not previously displayed. In some embodiments,the work day date panes are expanded to be tall enough to display allvisual content items within the selected work day date pane or withinthe selected row of work day date panes.

In response to a determination by decision module 162 that the receivedrequest is a request to expand a weekend date pane, module 166 expandsall weekend panes having the same weekend date as the selected weekenddate pane. In other words, in response to a user selection of a Saturdaydate pane, the entire column of Saturday date panes is expanded, and inresponse to a user selection of a Sunday date pane, the entire column ofSunday date panes is expanded. Module 166 configures the computer toalso compacts, i.e. makes narrower, weekday date panes by an amountsufficient to make room on the display screen for the expanded weekenddate panes.

Decision module 168 configures a computer to determine whether a userrequest is received to compact an expanded date pane, either a workdaydate pane or a weekend date pane. In response to receipt of a userrequest to compact, control flows to back to decision module 156.Decision module 168 waits for a user input received requesting date paneexpansion, as indicated by module 170.

Overview of Process to Generate Calendar UI

FIG. 2 is an illustrative generalized flow diagram representing ingeneral terms activities performed by client devices and by a serversystem and the flow of information between them in accordance with someembodiments. The client devices comprise user devices, which are clientsof a server system. The client devices and the server system communicatewith each other over a network. The server system, which may include oneor more different computer systems, processes information received fromclient user devices and uses that information to provide information tothe user devices used by the devices to produce calendar UIs. The clientuser devices receive information from users and provide that informationto the server system for processing to generate calendar UIs on theclient user devices. Information received from multiple different userdevices may be used by the server system to generate a calendar UIversion that is delivered to multiple user devices. Thus, the serversystem may assemble a custom calendar UI version that is displayed bymultiple different user devices based upon user input received fromusers of a number of different user devices,

Generally speaking, activities of client devices and server system fallwithin two categories. The first category is generation and organizationof visual content items used to produce and display visual contentitems. The second category is producing search queries and thegeneration of custom calendar UI instances based upon the searchqueries.

Within the first category of activity involving generation andorganization of visual content items, block 604 represents in generalterms user activities involved with creation of code objects used toproduce visual content items displayed in a calendar UI. The codeobjects include information structures stored in a non-transitorycomputer readable storage device that are used by client devices togenerate visual content items on device screens. Users provideinformation that indicates attributes of visual content items which arestored within code objects that are later used to cause client devicesto the display of the visual content items. Many different users maygenerate code objects. The code objects are sent over a network to theserver system for processing.

Also within the first category of activity, block 606 represents ingeneral terms server system activities involved with organizing andmanagement of code objects created by users of client devices. Theserver system identifies searchable attribute information withinuser-created code objects and creates one or more searchable informationstructures used to search for code objects based upon attributes thatmay be specified in user search queries. In accordance with someembodiments, creating the one or more searchable information structuresinvolves chronologically ordering code objects based upon dateinformation associated with the code objects and performing forward andbackward chronological searches through the ordered code objects. Inaccordance with some embodiments, the searchable information structuresinclude one or more index structures.

Within the second category involving producing search queries andgenerating custom calendar UI instances based upon the search queries,block 608 represents in general terms one or more users creating searchqueries and sending the search queries to the server system. Searchqueries identify attributes to be matched with code object attributes tocreate calendar UI instances. Different users may define differentsearch queries used to produce different calendar UI instances. Clientuser devices send the search queries over the network to the serversystem.

Also within the second category of activity, block 610 represents ingeneral terms, server system activities involved in the use of the oneor more searchable information structures to identify code objects thathave attributes that match attributes identified within search queriesreceived from client user devices. Block 612 represents in general termsserver system activities involved with mapping code objects matched to asearch query to calendar UI date panes. Block 614 represents in generalterms the server system sending to client user devices indicia of thecode object mappings to client user devices for use in display of customcalendar UI instances on client user device display screens.

Also within the second category, block 616 represents in general termsclient user device activities using the object code mapping indiciareceived from the server system to calendar UI instances for display.The code objects mapped to date panes are used to produce correspondingmapped visual content items mapped to those date panes. Thus, visualcontent items produced using code objects defined by different users maybe incorporated into a custom calendar UI produced in response to asearch query.

UI to Create Visual Content Item

FIG. 3 is an illustrative drawing of an example of a first userinterface screen display 302 to receive user input to define a newvisual content item for display within a calendar UI in accordance withsome embodiments. More specifically, the first UI display 302 is used toreceive user entries to define a new code object (not shown) that isused to generate a visual content item in accordance with someembodiments. The dialog screen display 302 of FIG. 3 is displayed inresponse to a user selecting the numerical date within a calendar UIinstance such as that of FIG. 1A. In the example first user interfacedialog display 302, it is assumed that a project exists that is named,“Marketing & Sales Materials”, identified within a project field 304,and the UI screen display of FIG. 3 represents user activity to create anew visual content item that represents a new task, the “(unnamedtask)”, identified within a task field 306, associated with the project.The example first user interface screen display 302 indicates the nameof the task creator, the time of task creation and provides a photo ofthe task creator.

Selectable tabs along a top and bottom portions of the example first UIdisplay 302 permit a user to specify attributes of the task. In responseto user selection of a first tab 310, a pull-down menu (not shown) isdisplayed in which to select an assignee attribute associated with atask. In response to user selection of a second button 312, a pull-downmenu (not shown) is displayed in which to select a date pane attribute(e.g., a date) associated with the task item is to be displayed. Inresponse to user selection of a third button 316, a pull-down menu (notshown) is displayed in which to specify a search term to associate withthe task. In response to user selection of a third tab 318, a pull-downmenu (not shown) is displayed in which to specify an attachmentattribute. In response to user selection of a fifth button 324, apull-down menu (not shown) is displayed in which to specify additionalactions associated with the task attribute.

FIG. 4 is an illustrative drawing of an example expanded view of avisual content item 402 that can be created using the first UI display302 of FIG. 3 in accordance with some embodiments. Referring to theexample calendar UI of FIG. 1A, the July 1 date pane displays a visualcontent item labeled with the task, “Review Sales Presentation”, whichis shown in expanded form in FIG. 4 . The visual content item 402 isdisplayed in response to a user input to select, e.g., click on, thevisual content item labeled, “Review Sales Presentation” in the calendarUI display grid. The expanded visual content item 402 includes a taskfield 404 containing the task name, “Review Sales Presentation”. Theexpanded item 402 includes a status field 406 that indicates “Updatedwith new branding” and includes a check mark indicating that the taskhas been started. The expanded item 402 includes an attachment field 408indicating that a “Sales Presentation” attachment is provided. Theexpanded item 402 includes a revision history field 410 that showsnumerous revisions and the revision contributors. The revision historyfield 410 includes an image 412 associated with one the revisioncontributors. The expanded item 402 includes a comments field 414 inwhich users can enter comments. The expanded item includes a tag 416that can be used to provide a visual indication of the expanded item 402having a relationship with another visual content item, such as throughcolor coding, for example. Thus, it will be appreciated that users canmodify a visual content item after its initial creation, throughrevisions or comments or updating status, for example.

Code Object Used to Generate Visual Content Items

FIG. 5 is an illustrative drawing showing certain details of an examplecode object 502 stored in a non-transitory computer readable storagedevice (not shown) that can be used to generate a visual content item inaccordance with some embodiments. In accordance with some embodiments, acode object is adapted for use to generate a corresponding visualcontent item in that computer program code (not shown) configures aclient user device to interpret the code object in generating thecorresponding visual content item. It will be appreciated that visualcontent items are rendered in a user interface screen of an end-userdevice in real time during display of a calendar UI instance. Moreparticularly, in some embodiments a rendering engine, such as a browser(not shown), renders a calendar UI date pane display grid and renderscontent items displayed within individual date panes of the displaygrid. The rendering engine uses a code object, which is presented in aprogramming language such as JavaScript, which can be interpreted by abrowser, to guide the rendering of a visual content item thatcorresponds to the code object. A user can use a first user interfacescreen display like that of FIG. 3 to specify attribute values of avisual content item represented within a code object such as the examplecode object 502 of FIG. 5 , which in turn, is used to create acorresponding visual content item, such as the visual content item 402of FIG. 4 , within a date pane of a calendar UI instance

The example code object 502 is a “task” code object. The example codeobject 502 includes a first list of attributes 504. The attributes 504of example code object 502 include Name, Description, User-visiblenotification time, etc. Each attribute in the list can have auser-assigned (or default) attribute value associated with it. Someattributes within the code object 502, themselves, include attributes,An Attachments attribute is associated within the code object 502 with asecond list of attributes 506 that includes ID, Name, Type and Content.A Stories attribute is associated within the code object 502 with athird list of attributes 508 that includes ID, Creator and Content. AProjects attribute is associated within the code object 502 with afourth list of attributes 510 that includes ID and Name. In someembodiments, a user may assign attribute values to a code object througha user interface screen display like that of FIG. 3 , for example.

UI to Create Search Query

FIG. 6 is an illustrative drawing of an example second user interfacescreen display 802 to receive user input to specify a search query todefine a new calendar UI instance in accordance with some embodiments.In some embodiments, a user invokes the screen display 802 of FIG. 6 byclicking on a query menu selector button 110 shown in the upper rightcorner of the calendar UI of FIGS. 1A-1C. The query is used to determinevisual content items that will appear on a calendar UI.

The example second user interface screen display 802 includes multiplesearch fields that used to identify search attributes to be matched withattributes of one or more code objects used to generate correspondingvisual content items. A user can enter search attribute information intothe first search field 810 labeled, “Contains the words”, to include ina task attribute query a search for matches with any words in the name,description, or comments of previously created in a code object used toproduce a visual content item that represents a task, as well as thename of the Creator or Followers, or the Project Name. A user can entersearch attribute information into the second search field 812, “Assignedto”, to extend the search to code objects used to produce visual contentitems representing tasks assigned to particular individuals. A user canenter search attribute information into the third search field 814, “Inprojects”, to extend the search to code objects used to produce visualcontent items representing tasks assigned to particular projects. A usercan enter search attribute information into the fourth search field 816,“Tagged with”, to extend the search to code objects used to producevisual content items tagged with a particular word or phrase, forexample. A user can enter search attribute information into the fifthsearch field 818, “Attachments Only”, to extend the search to codeobjects used to produce visual content items that represent tasksassociated with an attachment. A user can enter search attributeinformation into the sixth search field 820, “Due within the Next”, toextend the search to code objects used to produce visual content itemsfor tasks that have been completed or to extend the search to tasks thatare incomplete. A user can enter search attribute information into theseventh search field 822, to extend the search to code objects used toproduce visual content items that represent tasks that have due dateswithin a specified date range. A user can enter search attributeinformation into the eighth search field 824, “In Teams”, to extend thesearch to code objects used to produce visual content items thatrepresent that tasks that are in projects that are in specified teams. Auser can enter search attribute information into the ninth search field828, “Search by another Field”, to display additional search fields.

A user-defined search query defined through user entries into theexample second user interface screen display 802, is stored innon-transitory computer readable storage device (not shown) and is usedto search for matches among one or more stored task objects, which inturn, are used to generate corresponding visual task items for displaywithin date panes of the calendar UI.

Producing Searchable Attribute Information

FIG. 7 is an illustrative flow diagram representing a server systemprocess 700 to produce a searchable attribute information structure inaccordance with some embodiments. The process 700 is described in thecontext of illustrative example code objects and attributes. Module 702configures a computer to select a code object from a code objectdatabase 704 stored in a non-transitory storage device 706. The storedcode objects may be created using the first user interface screendisplay described with reference to FIG. 3 . Module 708 configures acomputer to parse the selected object to identify code portions that canact as searchable object attributes (also referred to herein assearchable attributes). In some embodiments, the identified codeportions that can serve as searchable object attributes include one ormore of strings, time stamps, integers and Booleans, for example. In thecourse of identifying searchable attributes, module 708 strips out fromthe code object symbols such as pointers that are not useful assearchable attributes. Module 710 configures a computer to index theidentified searchable attributes to the code objects that theycorrespond to and stores the identified indexed searchable attributes ina searchable attribute database 712 within a non-transitory storagedevice 714.

In some embodiments, indexing involves associating searchable attributes(e.g., attrib-1, attrib-2, etc.) with unique identifiers (e.g., ID-1,ID-2, etc.) within the searchable attribute database 712 and associatingcorresponding code objects (obj-1, obj-2 . . . obj-N) with the sameunique identifiers (e.g., ID-1, ID-2, etc.) within the code objectdatabase 704. In some embodiments, the unique identifiers includenumerical identifiers. It will be appreciated that a given code objectmay correspond to multiple searchable attributes. Each searchableattribute is associated with the same unique identifier that isassociated with its corresponding code object. Thus, for example,assuming that object, obj-1, is associated with searchable attributes,attrib-1 and attrib-2, identifier ID-1 is associated both with obj-1 andwith attrib-1 and attrib-2.

Decision module 716 configures a computer to determine whether there areadditional code objects in the software database 704 to be processed. Ifyes, then control flow returns to module 702. If no, then control flowsto module 718, which waits for some time interval, which may be fixed orvariable, after which control again flows to decision module 714.

FIG. 8 is an illustrative drawing of a table that identifies multipledifferent kinds of example task attributes and provides briefdescriptions of some of them in accordance with some embodiments. Thesearchable attribute database 712 may include searchable code portionsthat correspond to one or more of these kinds of attributes. Of course,it will be appreciated that the same attribute type (e.g., task creationdate, comments or assignee) may be identified for each of multipledifferent code objects, but that these multiple different code objectsmay have different values for these attributes (e.g., a different date,different comments or a different assignee). Thus, as explained morefully below, a search query may match some of the attributescorresponding to some of the different code objects but not others.

Identifying Query Matches and Ordering Matching Code Objects

FIG. 9 is an illustrative flow diagram representing a server systemprocess 900 to match search query to code objects and to chronologicallyorder code objects in accordance with some embodiments. The process 900is explained in the context of illustrative example search query, codeobjects and attributes. Module 902 configures a computer to select asearch query from a search query data structure 904, such as a table,for example, stored in a non-transitory storage device 906. Multipleclient user devices may create the search queries stored within the datastructure 904 using the second user interface screen display describedwith reference to FIG. 6 . Module 908 configures a computer to match theattributes identified by the selected query to searchable attributeswithin the attribute database 712 to identify attributes that match thequery. The example matching code objects are ordered based upon theirassociated dates from the earliest date N through the latest date N+1.

The search query may include Boolean logic such as AND, OR and NOT toindicate require attributes for matching. For example, referring to theillustrative query displayed in the calendar UI of FIG. 1A, module 908configures the computer to search for attributes that include strings,date stamps or integers that match both “Weekly Marketing MeetingAgenda” and “Marketing & Sales Materials” or that match “Goals Q2 2014”.More particularly, for example, referring to the illustrative seconduser interface screen display of FIG. 6 , in accordance with someembodiments, each attribute field (e.g., contains the words, assignedto, in projects, etc.) has its own definition of whether it uses AND orOR to combine the inputs in that attribute field. In some embodiments,the AND/OR definition is user selectable. If the various attributes arecombined with AND, then they all need to match. If the variousattributes are combined with OR, then at least one needs to match. Forexample, in accordance with some embodiments, if “apples” and “bananas”is entered into field 810, and Jack and Jill is entered into filed 812,then field 810 has a definition that requires all of the words, whilefield 812 has a definition that requires at least one of the words. Sothis example search will find objects that have Both apples & bananas tosatisfy the constraints in field 810, AND either Jack or Jill to satisfythe constraints in field 812.

Attributes that are determined to match the selected query, togetherwith their associated identifiers, are stored in a data structure 910,such as a table, within a non-transitory storage device 912. In theillustrative example, attributes having ID-2, ID-4 and ID-X are some ofthe attributes determined to match the search query. Module 914configures the computer to identify code objects from the database 704that have attributes that correspond to the matching attributes withinthe data structure 910 and to store the corresponding code objects in adata structure 916, such as a table, within a non-transitory storagedevice 918. Each code object corresponds to a time, such as a calendardate. A user may define the date associated with a code object when theuser creates the code object. For example, the matching code objectidentified by ID-2 corresponds to date N+1. In some embodiments, module914 identifies corresponding code objects by comparing identifiersassociated with matching attributes with identifiers associated withstored code objects. Module 920 configures the computer tochronologically order a stored set 919 of the matching code objects fromthe data structure 916 within a non-transitory storage device 917.

In some embodiments, for example, a list of project names may bepresented to a user through a UI menu (not shown). Each project in thelist may correspond to an identifier. A user may select one or moreprojects from the list, which become part of the query. The identifiersassociated with the selected project names are used to locatecorresponding code objects.

It will be appreciated that each identified code object includes dateinformation that may have been specified by a user, or auto-generated,when the object was first created or subsequently modified. For example,a user may actuate tab 312 in the illustrative first user interfacescreen display shown in FIG. 3 to select a date. The example code objectcode of FIG. 5 includes date information. In accordance with someembodiments the code objects' date information is used to determinechronological ordering. Decision module 922 configures a computer todetermine whether there are additional code objects in the softwaredatabase 904 to be processed. If yes, then control flow returns tomodule 902. If no, then control flows to module 924, which waits forsome time interval, which may be fixed or variable, after which controlagain flows to decision module 922.

Forward and Reverse Chronological Search and Mapping

FIG. 10 is an illustrative drawing representing certain details of anexample chronologically ordered set of the code objects 1002 within acode object ordering information structure 1004 stored in a computerreadable storage device (not shown) produced according to the process900 of FIG. 9 in accordance with some embodiments. The examplechronologically ordered set of code objects 1002 are used to producecorresponding visual content items displayed within date panes of theexample calendar UI instance of FIG. 1A, which is produced on a clientuser device display screen. The example chronologically ordered set ofobjects 1002 will be used to explain use of forward and reverse mappingof visual content items to calendar panes in accordance with someembodiments.

More particularly, the example chronologically ordered set of codeobjects 1002 is shown stored in a table data structure that includes aleft side column that identifies multiple objects and a right side datecolumn that identifies associated dates. Different objects correspond todifferent object identifiers (IDs) that are shown with arbitrary valuesselected for the purpose of this example. Each object is associated witha date. For example, the object associated with ID3 is associated withthe date June 26. More specifically, the objects are orderedchronologically from an example earlier date, which is not specified inthe drawing, which is associated with the object having ID5, and whichis earlier than the date of the earliest date pane within the currentlyvisible date range of the example calendar UI of FIG. 1A, i.e. earlierthan June 17, to a later date, which is not specified, which isassociated with the object having ID19, and which is later than the dateof the latest date pane within the currently visible date range of theexample calendar UI of FIG. 1A, i.e. later than July 12.

It will be appreciated that certain objects within set 1002 areassociated with dates in the currently visible range of a client userdevice, and others are associated with dates that are outside thecurrently visible range. In accordance with some embodiments, differentclient devices may have different size viewing screens areas. A Browser,for example, running on a client device may determine the device'sviewing area, which in turn, may determine the range of currentlyvisible date panes on the device display screen.

Referring to both FIG. 1A and FIG. 10 , it will be appreciated, forexample, that object ID13 in the ordered set 1000 is mapped to date paneJune 30 in the calendar UI and that the object ID13 also is used by arendering engine, within a browser, for example, to generate the visualcontent item containing the message, “[10 m] Communicating/improving . .. ”.

The current date in the example calendar UI of FIG. 1A is selected toact as the reference date in the chronologically ordered set of objects1000 of FIG. 10 . The term ‘reference date’ is used to refer to a datethat demarcates a boundary between the forward and reverse searches.There is no requirement of an equal number of calendar date panes beingvisible before and after the reference date. Moreover, in accordancewith some embodiments, the reference date may determine the boundarybetween date panes within the currently visible range and date panesoutside that range. For example, the reference date may be specified asthe earliest date within a currently visible range of date panes. Incalendar UIs used for project management, for example, it sometimes isthe case that future dates may be more important to display than pastdates. Designating the reference date for display as the earliestcurrently available date ensures that at least most of the currentlyvisible date panes correspond to future dates.

The currently visible date range of calendar UI of FIG. 1A extends fromJune 15 to July 12. As will be more fully explained below, a forwardchronological search through the chronologically ordered set of objects1002 proceeds starting with object ID15 associated with the date July 1and then to object ID2 associated with July 4 and then to object ID19associated with some later date outside the currently visible date rangeof the calendar UI and then may proceed to additional objects (notshown) associated with later dates outside the currently visible daterange. Conversely, as will be explained more fully below, a reversechronological search through the chronologically ordered set of objects1002 proceeds starting with object ID13 associated with the date June 30and then proceeds to objects ID8, ID3, and ID4 associated with June 26and then to object ID9 associated with June 23 and may proceed toadditional objects (not shown) associated with earlier dates outside thecurrently visible date range.

The forward and reverse searches are used to map code objects, and thus,corresponding visual content items to date panes of a calendar UI. Morespecifically, code objects identified during the forward and reversesearches are mapped to date panes matching the dates associated with theidentified objects. Once the code objects have been mapped, a renderingengine uses the mapped code objects to generate corresponding visualcontent items within the mapped-to date panes.

FIG. 11 is an illustrative flow diagram representing a chronologicalsearch and mapping server system process 1100 in accordance with someembodiments. The process 1100 shall be explained with reference to theexample calendar UI of FIG. 1A and the example ordered set of the codeobjects 1002 of FIG. 10 . Module 1102 configures a computer to determinea reference date. The reference date may be the current date or someother default date or a may be a user selectable date, for example.Module 1104 configures a computer to determine prescribed forward andbackward date mapping ranges. The prescribed forward and backward datemapping ranges may be predetermined, fixed or user selectable, forexample.

A prescribed forward date mapping range ordinarily encompasses a rangeof date panes having dates after the latest currently visible calendarUI date pane. Conversely, a prescribed reverse date mapping rangeordinarily encompasses a range of date panes having dates before theearliest currently visible calendar UI date pane. In accordance withsome embodiments, visual content items are mapped to a sufficient numberof calendar display grid date panes in forward and reverse chronologicaldirections relative to the reference date so that a currently visibleportion of the calendar UI date pane display grid contains all visualcontent items that are determined to match the query for that visibleportion of the calendar UI. In addition, as explained above, the mappingmay proceed far enough in forward and reverse directions so that datepanes of a sufficient portion of the calendar UI that is not currentlyvisible are mapped-to so as to facilitate continuous scrolling. In otherwords, scrolling can proceed smoothly, i.e. without a user-perceptibledelay due to a need to update mapping of additional content items to bedisplayed, for some range of dates before and after the currentlyvisible range. The scrolling can occur vertically in week-by-weekincrements with no breaks or interruptions at month boundaries.

The range of date panes visible within an end-user device display screenmay vary depending upon screen dimensions. A browser, for example, maydynamically determine device screen size, and therefore, the number ofvisible panes. In accordance with some embodiments, a browser API isused to query the browser to determine the browser's viewable windowheight. A client system can receive from the server system indicia ofthe mappings of code objects to date panes and can use the referencedate and device screen size information to determine the currentlyvisible range of date panes. It will be appreciated that user input maybe received to cause the calendar UI instance to scroll or to jump todisplay a different date pane range.

The forward and reverse date ranges are selected so that mappingdeterminations are made not only for dates that are closest to thereference date, which are most likely to be currently visible, but alsoare made for dates sufficiently after and before the currently visibledate panes to ensure smooth continuous forward and reverse scrolling forat least some date distance outside the currently visible calendar UIdate range. For example a prescribed latest date of prescribed forwarddate range mapping may be selected to be sixty days after the referencedate, and a prescribed earliest date of prescribed backward date rangemapping may be selected to be sixty days before the reference date.

Module 1106 determines forward and reverse object count limits. Thechronological search and mapping process 1100 is branched into a forwardsearch and mapping process branch 1150 and a reverse search and mappingprocess branch 1160. Both the forward and reverse branches 1150, 1160are performed as a part of the search process 1100. The forward andreverse searches are performed in chunks according to the object countlimits

Referring now to the forward search and mapping process branch 1150,module 1108 configures a computer to select, from the ordered set of thecode objects 1002 of FIG. 10 , a code object associated with theearliest date equal to or later than the reference date. Module 1110maps the selected object to a date pane in the calendar UI that has thesame date that is associated with the selected object. Thus, forexample, assuming that module 1108 selects object ID15 from the objectset 1002 of FIG. 10 , module 1110 maps the selected object ID15 to datepane July 4 in the calendar UI of FIG. 1A.

Decision module 1112 increments a current forward count. Decision module1114 determines whether the forward count limit has been reached. Inresponse to a determination that the forward count limit has not beenreached, control flows back to module 1108 and a next later code objectis identified in the information structure 1004 and is mapped to acalendar UI date pane.

In response to a determination by decision module 1114 that the forwardcount limit has been reached, control flows to decision module 1116,which determines whether a latest date associated with a code objectthat has been mapped to a calendar UI date pane, is earlier than aprescribed latest date pane a calendar UI that is under construction. Itwill be appreciated that a calendar UI instance ordinarily includes bothdate panes that are currently visible and contiguous date panes that arenot currently visible, but that could become visible soon due to userscrolling, for example.

In response to a determination that the latest date associated with acode object that has been mapped to a calendar UI date pane, is earlierthan the prescribed latest date pane, control flows to module 1118,which configures the computer to reset the forward count and to causecontrol to flow to module 1108 to search for a next chunk of codeobjects. In response to a determination by decision module 1116 that thelatest date associated with a code object that has been mapped to acalendar UI date pane, is later than the prescribed latest date pane,the forward search ends.

Referring now to the reverse search and mapping process branch 1160, areverse chronological search, module 1128 configures a computer toselect, from the ordered set of the code objects 1002 of FIG. 10 , acode object associated with the latest date earlier than the referencedate. Module 1130 maps the selected object to a date pane in thecalendar UI that has the same date that is associated with the selectedobject. Thus, for example, assuming that module 1128 selects object ID13from the object set 1002 of FIG. 10 , module 1130 maps the selectedobject ID13 to date pane June 30 in the calendar UI of FIG. 1A. Decisionmodule 1132 increments a current reverse count. Decision module 1134determines whether the reverse count limit has been reached. In responseto a determination that the reverse count limit has not been reached,control flows back to module 1128 and a next later code object isidentified in the information structure 1004 and is mapped to a calendarUI date pane.

In response to a determination by decision module 1134 that the forwardcount limit has been reached, control flows to decision module 1136,which determines whether an earliest date associated with a code objectthat has been mapped to a calendar UI date pane, is later than aprescribed earliest date pane of a calendar UI that is underconstruction. As mentioned above, it will be understood that a calendarUI instance ordinarily includes both date panes that are currentlyvisible and contiguous date panes that are not currently visible, butthat could become visible soon due to user scrolling, for example.

In response to a determination that the earliest date associated with acode object that has been mapped to a calendar UI date pane, is laterthan the prescribed earliest date pane, control flows to module 1138,which configures the computer to reset the forward count and to causecontrol to flow to module 1128 to search for a next chunk of codeobjects. In response to a determination by decision module 1136 that theearliest date associated with a code object that has been mapped to acalendar UI date pane, is earlier than the prescribed earliest datepane, the reverse search ends.

Referring to the illustrative calendar UI information structure 1200 ofFIG. 12 , which is explained next, the forward search and mappingresults in association of code objects C1 to C9 with date panestructures, and the reverse search and mapping results in association ofcode objects C10 to C15 with date pane structures. The date panestructures of FIG. 12 correspond to visible date panes of FIG. 1A. Thecode objects C1 to C15 can be used to generate corresponding visualcontent items (not shown). It will be appreciated from the followingdiscussion that mapping code objects C1-C14 to chronologically ordereddate pane information structures 1210 in effect chronologically ordersthe code objects.

Calendar UI Information Structure

FIG. 12 is an illustrative drawing representing an example calendar UIinformation structure 1200 produced by a server system in accordancewith some embodiments. The calendar UI information structure 1200corresponds to the calendar UI instance 102 of FIG. 1A. The calendar UIinformation structure 1200 is stored in a non-transitory computerreadable storage device (not shown) and can be produced according to theprocess of FIGS. 6-7 and 9-11 . The calendar UI information structure1200 is produced in response to a user search query, and in turn, isused to populate the date panes of one or more calendar UI instancesproduced in response to the query. The calendar UI information structure1200 may be delivered by the server system over a network to clientdevices to guide them in mapping the code objects, and correspondingvisual content items produced using the code objects, to calendar UIdate panes. As will be explained more fully below, the calendar UIinformation structure 1200 is organized by individual dates and weeksrather than by months, which facilitates real-time incremental updatingof the calendar UI as a user changes a date range currently being viewedthrough scrolling, for example.

More specifically, the calendar UI information structure 1200 includes aplurality of date pane information structures 1210 represented by dotsin FIG. 12 that respectively correspond to date panes of a correspondingcalendar UI instance produced based upon the calendar UI informationstructure 1200. The dot locations in FIG. 12 correspond in general tothe location of the date numbers in the calendar UI instance 102 of FIG.1A. FIG. 13 is an illustrative drawing that represents an example datepane information structure 1210 in accordance with some embodiments. Theexample date pane date information structure 1210 corresponds to theJul. 22, 2014 date pane of the calendar UI of FIG. 1A. The example datepane date information structure 1210 includes a table structure 1210that associates a date field 1304 and a code object identifier field1306. The example date pane information structure 1210 associates thedate Jul. 22, 2014 with an identifier of a code object used to producethe visual content item identified as “Approval for Budget”, which isdisplayed in the Jul. 22, 2014 date pane of the calendar UI of FIG. 1A.Thus, the example date pane information structure 1210 contains indiciaof the date Jul. 22, 2014 that is used to associate the Jul. 22, 2014date pane of the calendar UI with the code object used to generate thevisual content item to be displayed in the July 22, 014 date pane of thecalendar UI. It will be appreciated that although only one code objectidentifier is associated with the example date pane informationstructure 1210, it possible to associate multiple code objectidentifiers, corresponding to multiple visual content identifiers, witha date pane information structure. For example, a date pane informationstructure (not shown) that corresponds to the Jul. 26, 2014 date pane ofthe calendar UI of FIG. 1A would associate the date Jul. 26, 2014 withmultiple code object identifiers.

Referring again to FIG. 12 , the calendar UI information structure 1200,in accordance with some embodiments, organizes date pane informationstructures 1210 into week-long date ordered rows, each starting withSunday and ending with Saturday. FIG. 12 shows an example calendar UIinformation structure 1200 having twenty-one rows, which correspond totwenty-one weeks. Assume for example, that a date range of the calendarUI information structure 1200 corresponding to rows 1-13 is currentlymapped to a corresponding calendar UI information structure of FIG. 1A.It will be appreciated that the calendar UI instance of FIG. 1A can bedisplayed on multiple different user devices, which may have differentscreen display sizes. Assume, for example, that a first user device (notshown) has a screen size large enough to display a first date range(date range 1) and that a second user device (not shown) has a screensize large enough to display a second date range (date range 1), andthat date range 1 is smaller than a date range 2. Referring to FIG. 12 ,further assume that date range 1 that is currently visible on thecalendar UI instance 102 displayed by the first user device correspondsto rows 5-8 of the calendar UI information structure 1200, and that daterange 2 that is currently visible on the calendar UI instance 102displayed by the second user device corresponds to rows 4-8 of thecalendar UI information structure 1200.

Although only four rows (rows 5-8) are visible in the first date range,and only five rows (4-8) are visible in the second date range, thecalendar UI information structure 1200 includes multiple additional rowscorresponding to dates earlier than the currently visible ranges andmultiple rows corresponding to dates later than the currently visibledate range that are mapped to code object identifiers matching thesearch request used to generate the calendar UI instance of FIG. 1A. Inthe example calendar UI information structure 1200, rows 1-13 have beenmapped, and rows −1 to −4 and rows +1 to +4 have not been mapped. Thatis, code object identifiers corresponding to code objects havingattributes that map attributes associated with the search request towhich the UI information structure 1200 have been mapped to date paneinformation structures 1210 of the UI information structure 1200.However, code objects have not been mapped to rows −1 to −4, listed herein reverse chronological date order. Likewise, code objects have notbeen mapped to rows +1 to +4 listed here in forward chronological dateorder.

It will be appreciated that mapping of code identifiers to date indiciaof the calendar UI information structured 1200 corresponding to datepanes of the calendar UI instance 102 of FIG. 1A that are not currentlyvisible facilitates speed of scrolling since the mapping occurs prior toa user actually requesting to view date panes. Moreover, it will beappreciated that in accordance with some embodiments, the calendar UIinformation structure 1200 organizes the rows independent of monthboundaries. Thus, scrolling can occur smoothly and continuously,row-by-row, without breaks to occurrences of date boundaries. Thissmooth continuous scrolling can create the impression to a user that thecalendar UI is infinitely scrollable in forward and reverse directions.

More particularly, the calendar UI information structure 1200 organizesrows in date order so that each row is preceded by a row correspondingto the immediately preceding week's dates and is followed by a rowcorresponding to the immediately following week's dates. As explainedabove, each date pane information structure 1210 corresponds to anindividual date pane in the calendar UI instance. The calendar UIinformation structure associates code objects C1-C14 with respectivedate pane information structures 1210 of the calendar UI informationstructure 1200. As mentioned above, the example calendar UI informationstructure 1200 of FIG. 12 corresponds to the calendar UI instance 102 ofFIG. 1A. Code objects C1-C14 mapped date pane information structures1210 of the calendar UI information structure 1200 correspond to visualinformation structures displayed within corresponding display panes ofthe calendar UI instance 102 of FIG. 1A. In order to simplify theexample and the drawing of FIG. 12 , only one code object is shownassociated with any given date pane information structure, although inthe example calendar UI instance 102 of FIG. 1A, date pane June 26actually is shown associated with three visual content items, each ofwhich corresponds to a different code object, for example.

In some embodiments, the calendar UI information structure 1200 includesa month demarcation indicator 1202, which includes an expanded dateindication that includes both the day and the month, used in determiningdate panes from which to begin and end incremental shading. In someembodiments, the calendar UI information structure also includes areference date indicator 1204 associated with a date pane informationstructure 1210 that is associated with a reference date.

Referring to rows 4-8 of the example calendar UI information structure1200, code object C11 visible in row 5 corresponds to visual contentitem displayed within the June 18 date pane of the calendar UI instance102 of FIG. 1A. Code object C10 visible in row 6 corresponds to thecontent item displayed within the June 23 date pane of the calendar UIinstance of FIG. 1A. Code object C1 visible in row 6 corresponds to themultiple visual content items displayed within the June 26 date pane ofthe calendar UI instance 102 of FIG. 1 . As mentioned above, in order tosimplify the example and the drawings, only one code object is shownassociated with the June 26 date pane structure even though in factthere are three code objects associated with the June 26 date panestructure, one per displayed visual content item. Code object C2 visiblein row 7 corresponds to the visual content item displayed within theJune 30 date pane of the calendar UI instance of FIG. 1A. Code object C3visible in row 7 corresponds to the visual content item displayed withinthe July 1 date pane of the calendar UI instance of FIG. 1A. Code objectC4 visible in row 7 corresponds to the visual content item displayedwithin the July 4 date pane of the calendar UI instance 102 of FIG. 1A.

As explained above, the example calendar UI information structure 1200also includes rows that correspond to calendar UI instance rows that arenot currently visible. In particular, rows 1-4 and 9-13 of the calendarUI information structure correspond to calendar UI instance 102 rowsthat are not visible. It can be seen that code objects C5-C9 are mappedto date pane structures associated with not visible rows 9-13, and thatcode objects C12-C15 are mapped to date pane structures associated withnot visible rows 1-4. Also, it can be seen that the illustrative examplecalendar UI information structure includes rows that have not beenmapped. Rows +1 to +4 have not been mapped to code object identifiers.Rows −1 to −4 have not been mapped to code object identifiers.

Thus, it will be appreciated that the calendar UI information structure1200 can be used to more efficiently scroll continuously scroll rows1-13. As scrolling of a visible calendar UI instance 102 progresses anda new row comes into view on a device display screen, the visual contentobjects associated with date pane information structures 1210 structuresof FIG. 12 corresponding to newly visible date panes of the calendar UIinstance 102 of FIG. 1A are used by a rendering engine to generatecorresponding visual content items within the newly appearing date panesof the calendar UI instance 102. However, scrolling cannot occursmoothly into rows +1 to +4 and rows −1 to −4, which have not beenmapped. More particularly, in response to a client user device requestto view rows within these ranges, the server system may invoke themapping process of FIG. 11 to map additional rows of the informationstructure 1200 to the illustrative current calendar UI instance 102.

List View

FIG. 14 is an illustrative drawing of a list UI instance thatcorresponds to the calendar UI instance of FIG. 1A in accordance withsome embodiments. The example list view 1402 of FIG. 14 is producedusing the same example information structure 1200 of FIG. 12 that isused to produce the calendar UI instance 102 of FIG. 1A. It can be seen,for example, that the list view instance 1402 contains the same searchquery 1404 as the calendar UI instance 102: “Tasks in Weekly MarketingMeeting Agenda, Marketing & Sales Materials, or Goals Q2 2014”. Inaccordance with some embodiments, the list view contains a moreconsolidated view of the tasks and can be sorted in different orders(such as priority, or alphabetically) and navigated between with the upand down arrows of the keyboard.

FIG. 15 is an illustrative flow diagram representing a process 1500 togenerate a list view UI instance in accordance with some embodiments.Module 1502 configures a computer to display a calendar UI instance suchas instance 102 in FIG. 1A, for example. Module 1504 configures thecomputer to receive user input to select a list view. Referring to theillustrative drawing of FIG. 1A, for example, a user may actuate thelist button 104 to select a list view UI. Module 1506 configures thecomputer to select the chronologically ordered mapped code objectswithin the calendar UI information structure 1200. Referring to theillustrative calendar UI information structure 1200 of FIG. 12 , forexample, code objects C1 to C15 are selected. Module 1508 configures thecomputer to use the selected chronologically ordered code objects togenerate a chronologically ordered list of visual content items fordisplay. For example, the selected chronologically ordered code objectscan be used to generate the illustrative list view UI instance of FIG.14 .

Use of Calendar UI Information Structure to Render Either Calendar UI orList UI Instance

FIG. 16 is an illustrative drawing representing rendering of alternativerepresentations of a calendar UI information structure of FIG. 12 inaccordance with some embodiments. The example calendar UI informationstructure 1200 of FIG. 12 is stored in a non-transitory storage device1602. A computer system 1604 hosts a rendering device 1606, such as aBrowser of an end-user device, for example. The rendering devicereceives the calendar UI information structure 1200 and uses it torender on a display screen 1608 either a calendar UI instance 102 ofFIG. 1A or to render on the same display screen 1608 a list UI instance1402 of FIG. 14 .

Screen Size

FIG. 17 is an illustrative drawing representing a client device process1700 to determine number of rows of a calendar UI instance to display inaccordance with some embodiments. Module 1702 configures a computer todetermine screen size using a browser API as explained above, forexample. Module 1704 configures the computer to receive the calendar UIinformation structure and to determine how many rows can fit within thescreen. Module 1706 configures the computer to render a currentlyvisible portion of the calendar UI instance based upon the number ofrows that are determined to fit within the screen size.

Referring to the example information structure of FIG. 12 , adetermination by module 1704 that a screen is large enough to displayfive rows might result in rows 4 to 8 being displayed simultaneously ona client device display screen. However, a determination by module 1704that a screen is large enough to display only four rows might result inonly rows 5 to 8 being displayed simultaneously. Thus, the number ofcalendar UI instance rows displayed may depend upon screen size.

Scroll vs. Jump

FIG. 18 is an illustrative drawing representing a process 1800 todetermine whether to display scrolling to a selected date pane or todisplay a jump to a selected date pane in accordance with someembodiments. Module 1802 configures a client user device (not shown) todisplay a calendar UI instance. Module 1804 configures the user deviceto receive user input to select a date outside of a currently visibleportion of the calendar UI instance. Referring to the example calendarUI instance 102 of FIG. 1A, for example, a user may use the dateselection field 106 to select a date range for the calendar UI instance.It will be appreciated that continuous scrolling may require a clientuser device to request code object information from a server device foruse to generate a display of a visual content item within a newlyvisible date pane, for example. Alternately, a server (not shown) mayproactively send to a user device code object information, without anaffirmative user device request for it, that is associated with datesadjacent to a currently visible date range so that a user device canimmediately use those code objects to generate new visual content itemsfor newly visible dates if a user scrolls in to those dates. Decisionmodule 1806, which may be implemented by a server, determines inresponse to a user device request for code object information, whetherthe newly selected date is within a contiguous currently mapped daterange. Referring to the illustrative calendar UI information structure1200 of FIG. 12 , for example, dates in weeks 1-13 are within the mappeddate range, and dates within weeks +1 to +4 and dates within weeks −1 to−4 are outside the currently mapped date range. In response to adetermination that the newly selected date is within the currentlymapped date range, module 1808 configures the server to send to a userdevice code object information used to generate visual content items forthe newly selected date. The user device uses the code objectinformation to display continuous scrolling of rows from a visibleportion of the calendar UI instance to a newly visible portion of thecalendar UI instance. It will be appreciated that continuous scrollingprovides a user with a sense of the continuity of time between the twodates. It will be appreciated that if a server proactively sends thecode object information to user device for a newly scrolled to daterange, then a user device need not request the code object informationin order to scroll. The newly selected date is set as the reference datewithin the newly visible portion. In response to a determination thatthe newly selected date is not within the contiguous currently mappeddate range, and instead is in an extended date range for which mappinginformation that has not been delivered to the user device, module 1810configures the server to provide additional calendar UI informationstructure information according to one or more of the process of FIGS.6-7 and 9-11 and to use the newly generated information to display ajump or scroll to a newly visible portion of the calendar UI instance.The newly selected date is set as the reference date within the newlyvisible portion.

Network Exchanges of Information

FIG. 19 is an illustrative drawing representing in a system 1900 inaccordance with some embodiments. Multiple user devices 1902-1 to 1902-ncommunicate code objects, search queries, and information indicatingmatching code objects, over a communications network 1904 with a server1906. The user devices 1902-1 to 1902-n may include any of numerouskinds of electronic devices such as a smartphone, media player, PersonalDigital Assistant (PDA), cellular telephone, web appliance, personalcomputer, laptop computer or tablet computing device, for example. Thecommunications network 104 may any one of a number of different types ofnetworks and corresponding network interfaces such as a local areanetwork (“LAN”), a wide area network (“WAN”), the Internet, mobiletelephone networks, Plain Old Telephone (POTS) networks, and wirelessdata networks (e.g., WiFi and WiMax networks). The network may usewell-known transfer protocols (e.g., HTTP. The server 1906 may includehardware computer systems disposed at one or more than one location andmay include virtual machines, for example.

An illustrative example of the operation of the system 1900 is explainedas follows. One or more of the user devices 1902-1 to 1902-n receiveuser input to create code objects that are used to generate visualcontent items. In accordance with some embodiments, the user inputindicates attributes of the code objects. The user input associates thecode objects with dates. In accordance with some embodiments, the userinput is used to define corresponding code objects used to generate thevisual content items. Arrows 1908 indicate that information indicativeof the defined code objects is sent over the network 1904 to server1906. The server 1906 stores the defined code objects 1910 innon-transitory storage device 1912. It is noted that some but notnecessarily all user devices send information to define code objects. Inthis example, user device 1902-2 does not send code object identifyinginformation. The server 1906 performs the processing to produce achronologically ordered set of the code objects 1914 such as that shownin the illustrative drawing of FIG. 10 .

One of the user devices, e.g. user device 1902-n, receives user input todefine a search query and as indicated by arrow 1916, sends the queryover the network 104 to the server 1906. The server 1906 performs theprocessing to produce a calendar UI information structure A118, such asthat shown in the illustrative drawing of FIG. 12 that can be used togenerate calendar UI information structure in response to the query. Asindicated by arrows 1920, the server 1906 sends over the network 104 toeach of multiple user devices 1902-1 to 1902-n information identifyingcode objects that match the search query and dates associated with thematching code objects for use in generating a calendar UI displayingvisual content items corresponding to the matching code objects withindate panes having the associated dates. Each user device 1902-1 to1902-n has a corresponding display device 1922-1 to 1922-n. Each userdevice 1902-1 to 1902-n that receives the matching code objects producesa calendar UI instance 1924- to 1924-n on its corresponding screen. Asexplained above, the server may from time-to-time send additional codeobjects to support user scrolling to different date ranges.Alternatively, the server 1906 may send the information identifyingmatching code objects and associated dates to only a subset of themultiple user devices 1902-1 to 1902-n.

Example Machine Architecture

FIG. 20 is an illustrative block diagram of machine in the example formof a computer system 2000 within which instructions, for causing themachine to perform any one or more of the methodologies discussedherein, may be executed. In alternative embodiments, the machineoperates as a standalone device or may be connected (e.g., networked) toother machines. In a networked deployment, the machine may operate inthe capacity of a server or a client machine in server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine may be a personal computer (PC), atablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), acellular telephone, a web appliance, a network router, switch or bridge,or any machine capable of executing instructions (sequential orotherwise) that specify actions to be taken by that machine. Further,while only a single machine is illustrated, the term “machine” shallalso be taken to include any collection of machines that individually orjointly execute a set (or multiple sets) of instructions to perform anyone or more of the methodologies discussed herein.

The example computer system 2000 includes a processor 2002 (e.g., acentral processing unit (CPU), a graphics processing unit (GPU) orboth), a main memory 2004 and a static memory 2006, which communicatewith each other via a bus 2008. The computer system 2000 may furtherinclude a video display unit 2010 (e.g., a liquid crystal display (LCD)or a cathode ray tube (CRT)). The computer system 2000 also includes analphanumeric input device 2012 (e.g., a keyboard), a user interface (UI)navigation device 2014 (e.g., a mouse), a disk drive unit 2016, a signalgeneration device 2018 (e.g., a speaker) and a network interface device2020 to send and receive code objects and search queries, andinformation indicating matching code objects, for example.

The foregoing description and drawings of embodiments in accordance withthe present invention are merely illustrative of the principles of theinvention. Therefore, it will be understood that various modificationscan be made to the embodiments by those skilled in the art withoutdeparting from the spirit and scope of the invention, which is definedin the appended claims.

What is claimed is:
 1. A method to produce a multi-user calendar interface, the method comprising: storing, by a server system, an information structure that associates attribute information with code objects, the code objects corresponding to tasks previously assigned to individual users, wherein the code objects are configured to facilitate generation of visual content items corresponding to the tasks; receiving, at a user device associated with a first user, a search query input through a search interface, the search query identifying a second user and a third user; matching, at the server system, the second user and the third user identified in the search query with the attribute information stored by the server system to identify multiple ones of the code objects for multiple ones of the tasks previously assigned to the second user and the third user; in response to the matching, transmitting, by the server system to the user device, information that identifies the multiple ones of the code objects for the multiple ones of the tasks previously assigned to the second user and the third user; and in response to the transmitting, effectuating generation of a set of the visual content items for the multiple ones of the tasks previously assigned to the second user and the third user within a calendar date pane display grid of a multi-user calendar interface displayed via the user device, the set of the visual content items being generated in accordance with the multiple ones of the code objects for the multiple ones of the tasks previously assigned to the second user and the third user such that a first subset of the set of the visual content items associated with the second user include indicia identifying the second user, and a second subset of the set of the visual content items associated with the third user include indicia identifying the third user, the calendar date pane display grid comprising a two-dimensional display grid of date panes that individually correspond to individual days of a month.
 2. The method of claim 1, wherein generating the set of the visual content items includes displaying representations of status values of the multiple ones of the tasks.
 3. The method of claim 1, further comprising: chronologically ordering the multiple ones of the code objects into an ordered structure; and using the ordered structure to map the set of the visual content items to the multi-user calendar interface.
 4. The method of claim 1, wherein the multiple ones of the code objects identified by the server system are associated with dates within a prescribed date range, and wherein the method further comprises: sending, by the user device, a request over a network to the server system for information indicating matching code objects associated with the dates within an extended date range that is outside of the prescribed date range; sending over the network by the server system to the user device, information that identifies at least one code object and at least one date within the extended date range; receiving over the network by the user device from the server system, the information that identifies the at least one code object and the at least one date within the extended date range; and using the at least one code object to generate at least one visual content item within the multi-user calendar interface.
 5. The method of claim 1, further comprising: sending over a network from different user devices to the server system, different code objects that are associated with dates, wherein the code objects are adapted for use to generate the visual content items on different user device display screens; and wherein receiving the information that identifies the multiple ones of the code objects that match the search query over the network from the server system includes receiving information sent over the network by the different user devices to the server system.
 6. The method of claim 1, wherein the search query identifies two or more of an individual task, a task deadline, a milestone, a keyword, or a person.
 7. The method of claim 1, further comprising: receiving, at the user device, the search query.
 8. The method of claim 1, further comprising: receiving, by the server system from a first user device, a first code object, wherein the first code object corresponds to a first task previously assigned to the second user, wherein the first code object has been used by the first user device to generate a first visual content item within a first user calendar interface on the first user device.
 9. The method of claim 8, further comprising: receiving, by the server system from a second user device, a second code object, wherein the second code object corresponds to a second task previously assigned to the third user, wherein the second code object has been used by the second user device to generate a second visual content item within a second user calendar interface on the second user device.
 10. A system configured to produce a multi-user calendar interface, the system comprising: one or more processors configured by machine-readable instructions to: store, by a server system, an information structure that associates attribute information with code objects, the code objects corresponding to tasks previously assigned to individual users, wherein the code objects are configured to facilitate generation of visual content items corresponding to the tasks; receive, at a user device associated with a first user, a search query input through a search interface, the search query identifying a second user and a third user; match, at the server system, the second user and the third user identified in the search query with the attribute information stored by the server system to identify multiple ones of the code objects for the multiple ones of the tasks previously assigned to the second user and the third user; in response to matching, transmit, by the server system to the user device, information that identifies the multiple ones of the code objects for the multiple ones of the tasks previously assigned to the second user and the third user; and in response to transmitting, effectuate generation of a set of the visual content items for the multiple ones of the tasks previously assigned to the second user and the third user within a calendar date pane display grid of a multi-user calendar interface displayed via the user device, the set of the visual content items being generated in accordance with the multiple ones of the code objects for the multiple ones of the tasks previously assigned to the second user and the third user such that a first subset of the set of the visual content items associated with the second user include indicia identifying the second user, and a second subset of the set of the visual content items associated with the third user include indicia identifying the third user, the calendar date pane display grid comprising a two-dimensional display grid of date panes that individually correspond to individual days of a month.
 11. The system of claim 10, wherein generating the set of the visual content items includes displaying representations of status values of the multiple ones of the tasks.
 12. The system of claim 10, wherein the one or more processors are further configured by the machine-readable instruction to: chronologically order the multiple ones of the code objects into an ordered structure; and use the ordered structure to map the set of the visual content items to the multi-user calendar interface.
 13. The system of claim 10, wherein the multiple ones of the code objects identified by the server system are associated with dates within a prescribed date range, and wherein the one or more processors are further configured by the machine-readable instruction to: send, by the user device, a request over a network to the server system for information indicating matching code objects associated with the dates within an extended date range that is outside of the prescribed date range; send over the network by the server system to the user device, information that identifies at least one code object and at least one date within the extended date range; receive over the network by the user device from the server system, the information that identifies the at least one code object and the at least one date within the extended date range; and use the at least one code object to generate at least one visual content item within the multi-user calendar interface.
 14. The system of claim 10, wherein the one or more processors are further configured by the machine-readable instruction to: send over a network from different user devices to the server system, different code objects that are associated with dates, wherein the code objects are adapted for use to generate the visual content items on different user device display screens; and wherein receiving the information that identifies the multiple ones of the code objects that match the search query over the network from the server system includes receiving information sent over the network by the different user devices to the server system.
 15. The system of claim 10, wherein the search query identifies two or more of an individual task, a task deadline, a milestone, a keyword, or a person.
 16. The system of claim 10, wherein the one or more processors are further configured by the machine-readable instruction to: receive, at the user device, the search query.
 17. The system of claim 10, wherein the one or more processors are further configured by the machine-readable instruction to: receive, by the server system from a first user device, a first code object, wherein the first code object corresponds to a first task previously assigned to the second user, wherein the first code object has been used by the first user device to generate a first visual content item within a first user calendar interface on the first user device.
 18. The system of claim 17, wherein the one or more processors are further configured by the machine-readable instruction to: receive, by the server system from a second user device, a second code object, wherein the second code object corresponds to a second task previously assigned to the third user, wherein the second code object has been used by the second user device to generate a second visual content item within a second user calendar interface on the second user device. 